System and method for expediting purchase of vehicular insurance

ABSTRACT

A mobile application for purchasing vehicular insurance without the need for manual data entry via a mobile device keyboard is disclosed. The mobile application is configured to image driver&#39;s licenses and vehicle barcodes to collect relevant driver and vehicular information. Other relevant data is either collected from correlated third-party databases or user input via voice recognition or user-friendly graphical user interface screens. Collected information is transmitted to one or more insurers and one or more quotes are displayed for consideration by the applicant. The mobile application may further comprise payment services and insurance agency point of sale services. The mobile application further provides an interactive digital insurance identification card to serve as a platform and dashboard for readily accessing services associated with the insurance policy, particularly when in an accident, when roadside services are required, and when a lower cost updated policy is available to the insured party.

INCORPORATION BY REFERENCE TO ANY PRIORITY APPLICATIONS

Any and all applications for which a foreign or domestic priority claimis identified in the Application Data Sheet as filed with the presentapplication are hereby incorporated by reference under 37 CFR 1.57.

FIELD

The invention relates to systems and methods for purchasing insurancefor vehicles. More particularly, the invention relates to aconsumer-centric insurance point of sale application for mobile devicesused to remotely underwrite and purchase vehicle insurance.

BACKGROUND

There exists a significant unmet need for streamlining the process ofapplying for and processing vehicle insurance policy applications.Insurance providers require certain information to insure against riskin return for a premium. Typically, the information necessary for aninsurance quote (i.e. client age, marital, status, make, coverageoptions and vehicle year, and model) is input manually into a databaseusing a computer keyboard or a touch screen keypad on mobile devices.The potential customer may then be instructed to gather and/or provideadditional information.

Most consumers find it difficult and time consuming to collect allinformation needed when applying for a new vehicle insurance policy, andmay fail to complete the application process because one or more piecesof information are missing or difficult to obtain. Further, thecollection and processing of this information can be time consuming andcomplex, involving many manual steps and duplicative actions on the partof the potential customer and the insurance provider. Further, suchinformation is typically input manually into a database using a computerkeyboard or a touch screen keypad on mobile devices, either by thepotential customer searching for insurance, or by the insuranceprovider, if contacted by the potential customer.

Furthermore, even when the consumer has completed an application, theinformation must be verified by the insurance company receiving theapplication. Verification requires the comparison of informationcollected from the consumer to information about the consumer that theinsurance company is able to obtain from other third party databases.These other databases include, but need not be limited to, driverlicense databases, state accident and vehicle ownership databases,federal databases, criminal record databases, judicial databases, creditrecord databases and other public, commercial and private databases.Without seamless integration and access, significant additional time isrequired to process the insurance application, during which the consumermay lose interest in obtaining the policy.

Still further, when a consumer receives a valid quote for a vehicleinsurance policy from an individual insurance company, there is no wayto determine whether that coverage and cost presented in the quote isthe best as compared to what might be available from other companies.Consequently, due to the inconvenience associated with submittingapplications to other insurance companies, a consumer is likely toaccept the first quote, although it might not be the best.

Completing forms on a mobile device using the keyboard of the mobiledevice is difficult. Completing data fields using a keyboard typicallyresults in a high rate of human error in data acquisition and entry.Consequently, it is clear that there exists a substantial unmet need fora simple, user-friendly mobile insurance point of sale system that willallow a user to submit all data without typing using the keyboard of themobile device. There is a further need for such a system that willprovide an expedited approach to verify that the data collected usingthe mobile device can be confirmed as authentic and accurate. Stillfurther, to expedite the selection and purchase of vehicle insurance, itwould be desirable to have a consumer-centric system that issufficiently competent and comprehensive to eliminate the need for theparticipation of a middle man, i.e., an insurance agent, other than fora final review of submitted data to support underwriting and issuance ofa the final binding insurance policy. Further, there is a need for sucha system capable of taking all data input without requiring use of akeyboard.

There exist various disclosures that present features to support onlineapplication for vehicle insurance. For example, U.S. Pat. App. No.2013/0204645, Mobile Insurance Platform System, from Matthew DanielLehman et al, and assigned to Progressive Casualty Insurance Company,discloses a mobile insurance platform system that broadly addresses aplurality of different means for collecting data using a mobile devicefor the purposing of submitting insurance claims and for obtainingquotes for insurance coverage. Despite the breadth of the description ofthe invention of Lehman, the described system fails to provide asolution that is capable of expediting the insurance coverage process,eliminating errors and eliminating the need for participation by amiddle man, e.g., the insurance agent. In addition, the disclosure ofLehman does not address methods for ensuring accuracy of data submittedand avoidance of the use of a keyboard on the mobile device. Further,the disclosure of Lehman does not disclose a virtual interactiveinsurance identification card. Further, the disclosure of Lehmandescribes an extensive insurance application network architecturedesigned to support multiple insurance functions beyond acquiringvehicular insurance.

U.S. Pat. No. 8,401,878 B2, “Method and System for Connecting an Insuredto an Insurer Using a Mobile Device” to Stender et al discloses a mobileinterface between parties to an insurance transaction. As with thedisclosure by Lehman et al described above, the disclosure by Stenderincludes features beyond that of merely purchasing an insurance policy,to include submittal of claims and to support types of insurances beyondautomobile insurance. The disclosure of Stender et al likewise does notaddress the provision of a virtual interactive insurance identificationcard.

U.S. Pat. No. 8,340,83 B2, “Method and System for Furnishing an On-lineQuote for an Insurance Product,” to Grover et al and assigned to TheTravelers Indemnity Company, discloses an on-line insurance quotingsystem that requires a user to input data into a web application via akeyboard. The disclosure of Grover et al does not describe the use of amobile device for inputting and communicating data to an insurer. Alldata entry by a user of the system is manual.

U.S. Pat. No. 8,255,243 B2, “System and Method for InsuranceUnderwriting and Rating,” to Raines et al and assigned to Carfax, Inc.,discloses a system, apparatus and method focused on gathering dataassociated with a motor vehicle, primarily based on the VehicleIdentification Number (VIN). The disclosure of Raines is directed tovehicle information and does not describe features or functionality tosupport the use of a mobile device by a consumer to apply for and bindautomobile insurance. There exist a number of insurance apps that can beobtained for use on an IPAD, IPHONE, ANDROID or other mobile device. Forexample, GEICO provides GEICO Mobile, a mobile app available on the iPADand iPHONE. GEICO Mobile is an all-inclusive app to support access tostatic insurance ID Cards, billing, policy, claims, glass damage,roadside assistance, accident assistance and other consumer-centricinsurance interests. The GEICO Mobile app is not dedicated to automatedcollection of information to support expediting application for andbinding of an insurance policy, along with ensuring accuracy ofcollected and input data.

Other insurance companies, including STATE FARM, THE GENERAL,PROGRESSIVE, ALLSTATE, ESURANCE, NATIONWIDE, FARMERS INSURANCE, 21STCENTURY INSURANCE and others provide similar mobile apps for use on aniPHONE and iPAD. None of the above emphasize accuracy of data input nordo they contemplate inclusion of a virtual interactive insuranceidentification card.

Other software applications, in this case, mobile software apps, existthat purport to provide a means for comparing quotes from multipleinsurance carriers. However, our research indicates that these appsmerely take you to the site of a desired insurance carrier and fail toaggregate data from multiple quotes for comparison.

Hence, a need exists for an insurance point of sale system and methodthat enables faster and more efficient interactions than currentlyavailable. In addition, a need exists for a mobile insurance point ofsale system that utilizes scanning and other technology resident in auser's mobile device to eliminate typing or manual entry of insurancedata necessary to obtain an insurance rating, a price for the proposedpolicy and finally a binding agreement for insurance coverage. Stillfurther, there exists a substantial unmet need for such a system capableof providing timely and periodic assessment of improved insurancepolicies based on either coverage or price. Further, a need exists forsuch a system and method that can provide multiple insurance quotes to auser from multiple providers based on automated data input with minimalmanual entry by the user. Still further, a need exists for such a systemand method that will allow a user to directly and conveniently purchaseinsurance from a mobile device. Finally, a need exists for a virtualinteractive insurance identification card that simplifies interaction bythe insured user after obtaining coverage.

SUMMARY

The present invention is a system and method for expediting vehicleinsurance purchases using a mobile device while reducing input errors.The method and system is further applicable to purchasing other types ofinsurance. A potential customer, insurance applicant, or agent,hereinafter, a “user,” is able to rate and purchase insurance with amobile computing device, such as a smart phone. A user wishing topurchase vehicular insurance, according to the system and method of thepresent invention, is able to avoid visiting the office of an insuranceagent. Likewise, the present invention avoids the need for an insuranceagent to visit the user. Further, a user need not have a laptop ordesktop computer t to purchase vehicular insurance. Every aspect of theinsurance transaction may be completed via the user's mobile device,such as a smartphone or tablet. Additionally, even where the mobiledevice does not have cellular connectivity, Wi-Fi wireless connectivitymay be used.

The present invention provides a more efficient, convenient, and lesserror-prone alternative to current methods of: a) obtaining insurancequotes, b) comparing multiple quotes, c) purchasing insurance, d)obtaining updated insurance quotes, and e) accessing various servicesassociated with insurance coverage via a digital insurance ID anddashboard. The present invention expedites the insurance application andbinding process. In addition, the invention avoids the entry ofincorrect information which decelerates the application and bindingprocess via the integration of several features and functions used toqualify and confirm the accuracy and legitimacy of all informationgathered from an applicant for insurance. The present invention relieson input methods that eschew the use of a textual or QWERTY keyboard,thereby eliminating the inevitable input of incorrect information causedby the use of a small keyboard on a mobile device.

According to an embodiment of the invention, a user collects necessaryinformation using a mobile device configured to execute and run apurpose-built point-of-sale software application for that purpose,hereinafter the “POS application.” A user is typically an insuranceapplicant, but in other embodiments, the invention supports use by aninsurance agent. The POS application likewise is configured to transmitcollected information to other components of the system that process thedata either locally or remotely. For example, a user will scan adriver's license using the POS application on a mobile device, e.g., asmart phone and extract relevant driver information that can then beused to obtain additional driver information from other remote sources.

Likewise, a user will scan a vehicle barcode and vehicle identificationnumber, i.e., the VIN, using the POS application with the mobile device.The POS application then causes certain collected information to betransmitted to a central processing center of one or more potentialinsurers or a cloud-based server structure that runs and maintains thequote engine for one or more insurance providers. A centralized serverprocesses and verifies the submitted information where a quote engineapplies various pricing and coverage algorithms, and finally, one ormore quotes are then transmitted for display to the user applicant. Ifthe applicant confirms and approves one of the quotes, the systemcommunicates with the selected insurance provider and causes theinsurance provider to create an insurance policy and forward theultimate policy to the applicant along with a request for signature andpayment via credit card or other electronic method. The POS applicationprocesses payment and once payment has been received and confirmed bythe insurer, a digital virtual interactive insurance verification cardis issued to the applicant via the POS application. The digital virtualinteractive insurance verification card serves as a convenient andeffective dashboard through which the insured user is subsequently ableto access all information and services associated with their insurancepolicy and coverage without having to use the original POS application.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other features, aspects and advantages of various embodimentsof the present invention will become better understood with regard tothe following description, appended claims, and accompanying drawingswhere:

FIG. 1 is a diagram of the system relating the primary parties andcomponents associated with creation of an insurance policy, according tothe present invention;

FIG. 2 is a diagram of various elements of a mobile computing device andsupportive network infrastructure and peripherals utilized by thesystem, according to the present invention;

FIG. 3 is a flowchart of the insurance quote generation and acceptancemethod, according to the present invention;

FIG. 4 is a diagram illustrating the simultaneous generation andpresentation of insurance quotes from a plurality of insurancecompanies, according to the present invention;

FIG. 5 is a diagram illustrating data collection resources associatedwith an exemplary quote engine, according to the present invention;

FIGS. 6A-6W are exemplary user interface screenshots associated with afirst embodiment, according to the present invention;

FIGS. 7A-7E are illustrations of a second embodiment supporting avirtual interactive insurance identification card and dashboardaccording to the present invention; and,

FIGS. 8A-8L are exemplary user interface screenshots associated with afurther embodiment, directed to use by agents, according to the presentinvention; and

FIGS. 9A-9C are exemplary user interface screenshots associated with thehome screen of a mobile operating system according to the presentinvention.

The accompanying drawings numbered herein are given by way ofillustration only and are not intended to be limitative to any extent.Commonly used reference numbers identify the same or equivalent parts ofthe claimed invention throughout the several Figures.

DETAILED DESCRIPTION

FIG. 1 through FIG. 9, wherein like parts are designated by likereference numerals throughout, illustrate example embodiments of amethod and system for efficiently purchasing vehicle insurance via amobile device according to the present invention with minimal data inputerrors. Although the present invention will be described with referenceto the example embodiments illustrated in the figures, it should beunderstood that many alternative forms can embody the present invention.One of skill in the art will additionally appreciate different ways toalter the parameters of the embodiments disclosed, such as the size,shape, or type of elements, graphic designs, organization or networkconnectivity, for example, in a manner still in keeping with the spiritand scope of the present invention.

Referring to FIG. 1, an embodiment of the system 10 as taught by theinvention is shown. A user 12 is an individual who may seek to obtain aninsurance quote 415 and eventual insurance policy 420 from an insurancecompany 400. Typically, the user 12 is an actual consumer, but, incertain embodiments, the user 12 may also be an agent obtaining andentering data on behalf of an applicant. The insurance quote 415 is anoffering of an insurance policy 420 covering one or more licenseddrivers 14 and vehicles 16. A licensed driver 14 is an individual with avalid driver's license 15 who will be covered by the insurance quote415, and may include the user 12 and other drivers 14 within the user 12household or company. A vehicle 16 is uniquely represented by a vehicleidentification number 17 (also referred to as a “VIN”). A vehicle 16 maybe further identified by a garage address 18 that is used to determineinsurance rates for a specific geographic area. The user 12 obtains aninsurance quote 415 by interacting with his or her mobile device 20configured to execute and run an insurance sales software application90, hereinafter, the mobile pant of sale or POS application 90.

The mobile computing device 20 may comprise a mobile telephone handset,a Personal Digital Assistant, or other mobile communication device.Further, the mobile device 20 may comprise any type of portable ormobile electronics device, such as for example a smartphone, a cellphone, a mobile telephone, personal digital assistant (PDA), laptopcomputer, tablet-style computer, or any other portable electronicdevice. For example, in some embodiments, the mobile device 20 may be asmart phone, such as an IPHONE by APPLE, a BLACKBERRY phone by RIM, aPALM phone, or a phone using an ANDROID, MICROSOFT, or SYMBIAN operatingsystem (OS), for example. In some embodiments, the mobile device 20 maybe a tablet, such as an IPAD by APPLE, a GALAXY by SAMSUNG, and LATITUDEST TABLET PC by DELL, for example.

The mobile device 20 includes a camera 37 or other imaging device, suchas a scanner. Images of the documents taken using the mobile device 20or downloaded to the mobile device 20 can be transmitted to a systemremote server 86 via a computer network 80. The network 80 comprises oneor more wireless and/or wired network connections. For example, in somecases, images and other data can be transmitted over a mobilecommunication device network 42, such as a cellular telephone network,other mobile telephone network or via communication via a wirelessaccess point based on Wi-Fi or other similar technology. A modem 44 maybe used to facilitate data transmission across one or more of thenetwork communication protocols 42. The computer network 80 can alsocomprise one or more connections across the Internet 82.

A memory unit 60 associated with the mobile device 20 may store a mobilepoint of sale insurance software application 90 (hereinafter, a POSapplication 90) as discussed below. Memory unit 60 may include randomaccess memory 62 and read only memory 64. Further, memory unit 60 maycomprise any one or more devices suitable for storing electronic data,e.g., RAM, DRAM, ROM, internal flash memory, external flash memory cards(e.g., Multi Media Card (MMC), Reduced-Size MMC (RS-MMC), Secure Digital(SD), MiniSD, MicroSD, Compact Flash, Ultra Compact Flash, Sony MemoryStick, etc.), SIM memory, and/or any other type of volatile ornon-volatile memory or storage device. The POS application 90 may beembodied in any combination of software, firmware, and/or any other typeof computer-readable instructions.

The POS application 90 and/or any related, required, or usefulapplications, plug-ins, readers, viewers, updates, patches, or othercode for executing the POS application 90 may be downloaded via theInternet or installed on mobile device 20 in any other known manner.

A central processing unit 40 associated with the mobile device 20 mayinclude a microprocessor, a microcontroller, a digital signal processor(DSP), an application specific integrated controller (ASIC),electrically-programmable read-only memory (EPROM), or afield-programmable gate array (FPGA), or any other suitableprocessor(s), and may be generally operable to execute the POSapplication 90, as well as providing any other functions of mobiledevice 20.

The mobile POS application 90 comprises one or more software modulesthat reside in the memory 60 of the mobile device 20 and may beimplemented to execute the method taught by the invention. Throughoperation of the mobile POS application 90, the user 12 submits variousinformation via the mobile device 20 to the system 10 which captures thesubmitted information in a customer information database 405. Thecustomer information database 405 is a digital repository which receivesand stores applicant information. The system 10 likewise includes aquote engine 410 that processes user applicant information andsubsequently generates one or more insurance quotes 415 forconsideration by the user applicant 12. Each quote is based oninformation submitted by the user applicant 12 and additionalinformation obtained from other third-party databases related to theuser applicant 12 and the vehicle 16 to be insured. The quote engine 410generates one or more insurance quotes 415 and returns and displays thequotes 415 to the user applicant 12 via the display of the mobile device20. The user applicant 12 may then select and accept one of theinsurance quotes 415 via the touch screen of the mobile device 20. Thesystem will then cause a proposed insurance policy 420 to be created forfinal evaluation and potential execution by the user applicant 12 andthe insurance company 400.

Referring now to FIG. 2, a schematic of the extended architectureassociated with and supporting operation of the method and system 10 andthe mobile device 20 is described. The mobile device 20 may be a tablet,smart phone or mobile phone. The POS application 90 leverages thecapabilities of the mobile device 20, including: phone mode, voicerecorder mode, SMS text mode, e-mail mode, digital camera mode, digitalvideo recording mode, photograph gallery mode, video gallery mode, GPSmode, and other input devices, such as a touch screen, which minimizesthe effort to collect, coordinate, administer and manage the desireddata.

The mobile computing device 20 is configured to receive multiple formsof input 30, including but not limited to touch input 31, audio input 33(e.g., voice recognition), numeric keyboard input 35, and camera/scannerinput 37. The forms of input 30 used by the POS application 90 avoidmanual input by a user 12 using a QWERTY keyboard.

Output 50 modes include audio output 52 and visual output 54, leveragingthe display screen 55 and speakers of the mobile device 20,respectively. Visual output 54 can also be accomplished via delivery ofinformation by the POS application 90 to a printer 57. The mobilecomputing device 20 comprises a central processing unit (CPU) 40 with anarithmetic unit 41 for processing instructions associated with the POSapplication 90. Although not shown in the illustration, the mobilecomputing device 20 may include other customized chips that assist inencryption or rendering of imagery.

The mobile device 20 further includes a memory unit 60 comprised ofrandom access memory (RAM) 62 and read only memory (ROM) 64. The system10 may supplement the mobile device 20 via the availability of datastorage unit 70 to support various databases associated with the system10. The system data storage unit 70 may be a hard drive 72 or removablestorage 74. A hard drive 72 used for storage may be local or remote,connected to a network cloud storage 84 or network-attached storagedevice. The mobile device 20 may communicate via cellular, Wi-Fi,Ethernet or other applicable communication method 42 to reach a computernetwork 80 or the Internet 82.

Referring now to FIG. 3, a method 200 for rapidly obtaining an insurancequote 415 using a mobile computing device 20 while minimizing inputerrors and, where desirable, eliminating the need for interaction withinsurance agents, is shown. First, in step 205, an user applicant 12downloads a point-of-sale application 90 to the applicant's mobilecomputing device 20. The POS application 90 comprises one or moresoftware modules configured to run on any of a plurality of mobilesoftware environments including IOS, ANDROID, WINDOWS, and other mobiledevice operating systems.

In step 210, the user applicant 12 selects and launches the POSapplication 90 on their mobile device 20. In step 215, the POSapplication 90 confirms whether the user applicant 12 has previouslylogged into the system from a prior use. If the user applicant 12 hasnever logged in, in step 220 the POS application 90 prompts the userapplicant 12 for login credentials including an email address andtelephone number. When login credentials have been entered, or if theuser applicant 12 was logged in from a previous session, in step 225 theuser applicant 12 is presented with the submitted login credentials andprompted to confirm that the email address and telephone number areaccurate. If the login credentials are inaccurate, the user applicant 12is returned to step 220 to fix the error. Ideally, an email address isinputted using voice recognition to capture each letter, number andsymbol associated with the email address.

Likewise, the applicant's telephone number is inputted using eithervoice recognition or a numeric keypad displayed on the screen of themobile device 20, wherein the layout is equivalent to the dialing pad ofa standard telephone. Various functions may be implemented after thesubmittal of email and telephone number to further qualify and confirmthat the applicant is legitimate. In one instance, the POS application90 will cause a confirmatory email to be sent to the email addressprovided. In another instance, the POS application 90 will cause aconfirmatory text message or voice call to be transmitted to the userapplicant 12. In an additional instance, two or more of these confirmingmethods may be used to confirm and qualify the identity of the userapplicant 12.

Where available, the POS application 90 will confirm the geographiclocation of the user applicant 12 using GPS capability resident withinthe mobile device 20. Further, where access is authorized, the POSapplication 90 may collect both email address and phone number frominformation resident in the memory 60 of the mobile device 20.

Next, after having logged into the POS application 90, in step 230, theuser applicant 12 is prompted to scan a licensed driver 14 driverlicense 15 via the camera 37. Typically the first driver license 15scanned will be that of the user applicant 12. The mobile device 20processes the captured image of the licensed driver 14 and extractsrelevant information from the driver's license 15, including thelicensed driver 14 name, address, age, gender, and other relevantinformation. In step 235, the user applicant 12 is presented with theextracted driver's license information and provided the opportunity toidentify and correct any input errors caused by imperfect scanning. Instep 240, the user applicant 12 is given the opportunity to scanadditional driver licenses 15 representing additional drivers 14. Ifthere are additional licensed drivers 14, the user applicant 12 mayrepeat the license imaging process from step 230 as needed. When alldriver's licenses 15 have been imaged, imported and validated, in step245, the POS application 90 causes the submitted data to be securelytransmitted to a customer information database 405. The customerinformation database 405 may reside on a storage resource and serverassociated with an insurance provider 400 or with the system 10 foraccess by one or more insurance providers 400.

Still referring to FIG. 3, in step 250, the user applicant 12 isprompted to enter vehicle information. In step 250, the user applicant12 uses the mobile device 20 to image or scan a vehicle identificationnumber 17 using the camera 37. In step 255, the mobile device 20attempts to process the image to extract the vehicle identificationnumber 17. If the scan was unable to extract a vehicle identificationnumber (“VIN”), the user applicant 12 is prompted to try again at step250. If the VIN scan was completed successfully, in step 260 the mobiledevice 90 parses the scanned VIN 17 to identify the year, make, andmodel of the vehicle 16. In step 265, the user applicant 12 is promptedto scan additional VIN numbers 17, if the user applicant 12 has othervehicles that he wishes to insure, repeating from step 250 as necessary.

Once all vehicles 16 have been added, in step 270, the user applicant 12is prompted to confirm the garage address 18 corresponding to eachvehicle 16. The user applicant 12 may assign each vehicle 16 to anyaddress previously identified during step 230, or, the applicant maysubmit an alternative garage address 18 using voice recognition orselection from a digital map. In step 275, the POS application 90 causesall VIN numbers 17 and associated garage addresses 18 to be transmittedacross the network 80 and stored in the customer information database405. In step 280, the user applicant 12 is prompted to complete the POSapplication process 200 by providing any additional information,accepting terms and conditions, and any other necessary application stepprior to generating a quote. In each of these elements, additionalinformation is preferably provided via voice recognition, interactionwith screen choices, or biometric scanning.

Based on the licensed driver 14 and vehicle 16 information provided tothe customer information database 405, a quote engine 410 generates oneor more of insurance quotes 415 to be made available to the userapplicant 12. In step 285, the system 10 causes the quote engine 410 totransmit data associated with the insurance quotes 415 to the mobiledevice 20 where the POS application 90 causes the one or more quotes tobe displayed to the user applicant 12. In step 290, the user applicant12 is prompted by the POS application 90 to select an insurance quote415 from the available list. If the user applicant 12 indicates thatthere are no satisfactory insurance quotes 415, in step 295, theapplication process is aborted and canceled.

If the user applicant 12 does find a satisfactory insurance quote 415,in step 300 the user applicant 12 is prompted to confirm thetransaction, select payment options and finalize the transaction. If theuser applicant 12 declines to finalize the transaction, in step 295, thesystem 10 causes the transaction to be cancelled. If the user applicant12 elects to confirm the transaction, in step 305, the user applicant 12is prompted to scan a credit card using the camera 37 associated withthe mobile device 20, or, select another payment method. Finally, thetransaction is recorded and sent to the customer information database405 for final processing.

Next, in step 310, the POS application 90 generates a temporary digitalinsurance identification card that contains relevant coverageinformation and serves as temporary proof of insurance until a completeinsurance policy 420 is finalized and confirmed. The temporary digitalinsurance identification card may be displayed on the display screen ofthe mobile device 20.

Referring still to FIG. 3, in step 315, the insurance company 400 thatissued the accepted insurance quote 415 reviews the terms of the quoteand creates an insurance policy 420 between the user applicant 12 andthe insurance company 400. In step 320, the issuing insurance company400 authorizes the POS application 90 to create and display to the userapplicant 12, now the insured, an official permanent digital insuranceidentification card referencing the confirmed insurance policy 420. Thepermanent digital identification card may be sent via email or madeavailable for scanning and display from within the POS application 90.In step 325, the system 10 allows the issuing insurance company 400 toelect to send a physical copy of the permanent insurance ID card bypostal mail or other carrier to the insured user applicant 12.

Referring now to FIG. 4, in one embodiment of the system 10, the mobilePOS application 90 will present one or more insurance quotes 415 fromone or more multiple different insurance companies 400 simultaneously tothe user applicant 12. According to the embodiment, the mobile device 20simultaneously sends user data to a plurality of distinct customerinformation databases 405, each managed by a unique insurance company400. Each insurance company 400 then processes the input user data viaits own quote engine 410. The various quote engines 410 may followdifferent pricing protocols in generating insurance quotes, leading to aplurality of differing insurance quotes 415 generated by each insurancecompany 400. The data associated with the insurance quotes 415 from eachinsurance company 400 are aggregated 417 and transmitted to the mobiledevice 20 for further processing by the mobile POS application 90 toprovide a table 422 for comparison of each of the proffered insurancequotes 415. The user applicant 12 may select one of these insurancequotes 415 to generate an insurance policy 420. The insurance policy 420will be formed between the user applicant 12 and the insurance company400 that presented the accepted insurance quote 415.

Referring now to FIG. 5, the quote engine 410 comprises one or moresoftware-based algorithms configured to generate an insurance quote 415based on data associated with input from a user applicant 12. As one ofthe objectives of the invention is to minimize errors in the creation ofinsurance quotes 415, the data collection process relies on informationfrom sources other than data inputted manually by a user applicant 12using a keyboard. For instance, rather than having a user 12 manuallyenter the vehicle make and year, or in the alternative manually enterthe VIN 17, the vehicle make and year are extracted automatically fromthe scanned VIN 17. In a preferred embodiment, the POS application 90will not allow an applicant to input the VIN 17 manually. Although thisrequirement might result in instances wherein the POS application 90 isunable to collect required data, where data is confirmed, the system 10,user applicant 12 and insurance company 400 will benefit from theaccuracy of the collected data. In the event a user applicant 12 isencountering difficulties using the POS application 90 on the mobiledevice 20 to collect information, the system 10 will determine whetherthe POS application 90 is either out-of-date or corrupted and willdirect the user applicant 12 to download a new or updated version of thePOS application 90.

The quote engine 410 is configured to generate an initial quote 415using information scanned from the VIN 17 and the applicant's driver'slicense 15. Information concerning licensed drivers 14 and vehicles 16are routinely collected by a plurality of reporting agencies. Theseagencies may produce reports on a licensed driver 14 or vehicle 16including DMV records 425 provided by a state DMV, police records 430provided by police departments, vehicle history reports 435 provided byvarious private companies and user applicant credit records 440.

In the context of a driver's license 15, information presented on thefront of the license 15 is available through imaging or scanning of abar code on the back of the license 15. Scanning the bar code will causethe various fields in the insurance application to be populated with theappropriate information.

Vehicle history information comes from many sources including records onfile from NMVTIS, state DMV, police records, fire & insurance records,data aggregators as well as many other proprietary sources. The NationalMotor Vehicle Title Information System (NMVTIS) is a databaseadministered by the American Association of Motor Vehicle Administrators(AAMVA) & overseen by the US Department of Justice. NMVTIS is the onlyvehicle history database in the nation in to which all states, insurancecarriers, & junk salvage yards are required by federal law to reporttheir data. Accessing and correlating data via the NMVTIS will allowincorrect information to be flagged and corrected by the user applicant12, and, allow an insurance company 400 to confirm that the informationsubmitted by the user applicant 12 is accurate.

For example, the system 10 can access the NMVTIS to discover, amongother things: a) information from a vehicle's current title, includingthe vehicle's brand history, e.g., whether the vehicle has a status of“junk,” “salvage,” or “flood”; b) the latest reported odometer readings;c) any determination that the vehicle is “salvage” by an insurancecompany or a self-insuring organization, including those vehiclesdetermined to be a “total loss”; and any reports of the vehicle beingtransferred or sold to an vehicle recycler, junk yard or salvage yard.

In addition to accessing the NMVTIS, the system 10 will also supplementits records by accessing state vehicle records to confirm thatcompleteness of the information gathered from the NMVTIS. Additionally,the system 10 will access other commercial databases, such as CARFAX, asappropriate, to ensure a complete vehicle information record andhistory.

Reports may be generated for a licensed driver 14 or vehicle 16 usingonly the driver's license 15 or VIN 17, respectively. To ensureaccuracy, the POS application 90 does not provide for the entry of amanual driver's license number 15 or VIN 17. When a quote engine 410 istasked with generating an insurance quote 415, the quote engine mayextract additional information from these reports including drivingrecords, accident history, and vehicle health, without requiring theuser applicant 12 to manually enter the additional information. Instead,the user applicant 12 need only to scan the driver's license 15 and theVIN 17 as previously described.

In the event that the user applicant 12 is unable to submit informationvia the mobile device 20, the POS application 90 may display an iconthat can be triggered by the user applicant 12 to directly call a dataentry support person to assist in inputting all necessary information byspeaking with the support person. This feature ensures that the userapplicant 12 is able to submit information even where the mobile device20 is unable to image or scan necessary items such as the driver'slicense 15 and VIN 17. Once the user applicant 12 contacts the POSapplication 90 support person, the method 200 associated with theinvention is still implemented but the POS application 90 support personperforms all data entry for the user applicant 12. The system 10 willstill activate confirming and qualifying functions in the POSapplication 90 resident on the applicant's mobile device 20.

In a first embodiment, shown in FIGS. 6A-6W, exemplary views of agraphical user interface (hereinafter the “interface”) for userinteraction with the system 10 are shown. The illustrated interface areexemplary and other alternative interface designs and functionality maybe implemented in association with the invention.

In FIG. 6A, a user 12 is presented with a splash screen 1010 andprovided the options of starting the POS application 90, or going to aseparate web site or help page to learn more about the POS application90. When the user 12 selects the “Start” button 1020, the user 12 isthen presented with a login page interface, as shown in FIG. 6B, thatincludes terms of service and login fields 1030 requiring an emailaddress or username along with an associated password. The user 12 maythen accept the terms of service and sign in by touching the “Accept andSign In” button 1035.

In FIG. 6C, the user 12 is presented with a “Main Menu” page interface1100 which includes icons for selection: “My Drivers” 1120, “MyVehicles” 1130, “My Quotes” 1140, and “My Virtual ID” 1150. If the user12 selects the “Help” icon 1112, the application 90 presents a “HelpMenu” page interface 1160, illustrated in FIG. 6D, displaying varioushelp topics that can be selected by the user 12 for further information.The Help Menu 1160 will also provide a number to call support directly.

As shown in FIG. 6E, initially, the user 12 will select the “My Drivers”button 1120, wherein the POS application 90 will cause a “My Drivers”page interface 1200 to be presented to the user 12. At the My Driverspage 1200, the user 12 may be presented with a list of one or moredrivers 1210 and has the ability to view and edit information associatedwith each driver 14. In the event this is the first use of the POSapplication 90 by the user 12, the user 12 will initially select “AddNew Driver” 1214.

When the user 12 selects the “Add New Driver” button 1214, the POSapplication 90 will present a new “Add New Driver” interface page 1220on the display screen 55 of the mobile computing device 20, as shown inFIG. 6F. Here, the user 12 can elect to scan a driver's license bytouching the “Scan” button 1222, or upload an existing digital photo ofa driver's license by touching the “Upload License Photo” button 1224.In addition, the user 12 may select the “Virtual ID” button 1212 whichwill cause the POS application 90 to present a new interfaceillustrating the user 12 virtual interactive insurance identificationcard, as shown in FIG. 9A.

When adding a new driver 14, the POS application 90 presents a “Add NewDriver” interface 1220 to the user 12. By selecting the “Scan” button1222, the user 12 is presented with two interfaces 1230, 1235 shown inFIGS. 6G and 6H, which allow the user 12 to scan the front and rear ofthe driver's license 15. In FIG. 6G, when scanning the front of thedriver's license 15, the driver's image and textual data are acquired bythe mobile computing device 20 and textual data is optically recognizedusing optical character recognition software associated with the POSapplication 90. In FIG. 6H, when scanning the rear of the driver'slicense 15, one or more barcodes are imaged and then processed by thePOS application 90 to extract the relevant driver information. The datafrom the front scan and rear scan are then compared against each otherto ensure a match. If there are any discrepancies, the POS application90 will point out any inconsistencies and provide the user 12 with theopportunity to speak to a support person to rectify the inconsistencies.The POS application 90 will not allow the user 12 to proceed further inthe process until any discrepancies are resolved.

Referring now to FIGS. 61 and 6J, once discrepancies have beenrectified, if any existed, the data extracted from the front and rear ofthe driver's license is automatically populated in the data fields for“Driver Information” 1240. The user 12 is given an opportunity to reviewthe extracted information to ensure accuracy. If accurate, the user 12may then “Accept” the data in the fields, verifying accuracy and causingthe data to be stored in memory on the mobile computing device 20 foreventual transmission to one or more insurance companies 400.

Now, referring to FIG. 6K through 6P, exemplary user interface screensassociated with collecting and verifying vehicular information areillustrated. Selecting the “My Vehicles” button 1130 on the Main Menuinterface 1100 shown in FIG. 6C causes the POS application 90 to displaythe “My Vehicles” page 1300 to the user 12. At this page, the user 12can review a list of vehicles 1310 and view or edit any informationassociated with each of the vehicles 16 in the list. The user 12 ispresented with a vehicle image 1311 corresponding to the vehicle 16selected in the list. Selecting the “View/Edit” 1315 button will causean edit vehicle interface 1320 associated with the selected vehicle 16to be displayed where year, make model and VIN # can be edited by theuser, the vehicle 16 may be deleted from the list or the user 12 maymerely confirm that the information is accurate and return back to the“My Vehicles” page 1300.

If additional coverage is required for an additional or new vehicle 16,the user 12 can select the “Add New Vehicle” button 1314. This actionwill cause the POS application 90 to display an add new vehicleinterface 1330, as shown in FIG. 6M, where the user 12 can perform thosesteps necessary to collect information associated with the new vehicle16. First, the user 12 may elect to add a new photo for the vehicle 16or select photos corresponding to “Photo 1” and “Photo 2” from a galleryof vehicle photos 1331. Adding a new photo from device storage placesthe new photo in the gallery of vehicle photos 1331 for selection.

Next, the user 12 can elect to either “Scan VIN” 1332 of a new vehicle16 or “Upload VIN Photo” 1334. In either case, the POS application 90will extract the vehicular data from the image of the VIN tag andpopulate the vehicular data fields, as shown in FIG. 6N.

Referring now to FIG. 60, a “Scan Vehicle's Barcode” interface 1340 isshown. Here, using the camera 37 of the mobile computing device 20, theuser 12 positions the brackets 1347 on the interface such that the imageof the VIN tag of the vehicle fully incorporate and fill the area withinthe brackets. The user 12 then triggers the camera 37 using the buttonto capture a photo of the VIN tag. The POS application 90 then processesthe barcode and the numerical portion of the VIN tag to extractvehicular data. This information is then used to populate data fields inthe vehicle information review interface 1350 shown in FIG. 6P whichidentify the particular vehicle 16 for which insurance coverage is beingsought. At this juncture, the user 12 can “Accept” the information andthen, can elect to add another vehicle 16 to the list, by selecting “AddVehicle.”

In addition to imaging the VIN tag, the system can perform opticalcharacter recognition of the VIN 17 below the bar code, or, theapplicant can speak the numbers and letters provided below the barcodeinto the mobile computing device 20 to capture the VIN 17 to allowvehicular data to be extracted to populate the relevant data fields.

Having collected all driver 14 and vehicle 16 information via the POSapplication 90, the user 12 is returned to the Main Menu interface 1100where the “My Quotes” button 1140 may be selected to cause the POSapplication 90 to present a new interface, the “My Quotes” page 1400 tothe user 12, as shown in FIG. 6Q. Here, the user 12 may elect to get anew quote 1412, or view existing saved quotes 1414 for one or morevehicles.

If the user 12 elects to obtain a new quote 1412, the POS application 90presents a new user interface, shown in FIG. 6R, which provides alisting of coverage options 1420 available for selection by the user 12.After coverage options have been chosen, the user 12 can submit theinformation via the POS application 90 which transmits the informationcollected information to one or more insurance companies, agencies orcarriers 400. All information transmitted to the insurance company 400is sent via an encrypted link to protect the personal information of theuser 12 requesting insurance coverage.

If additional information is required by any of the insurance companies,agencies or carriers 400, an “Underwriting Questions” interface 1430 isdisplayed to the user 12. The questions are structured in a manner thatonly requires the user 12 to select a radio button, indicating “Yes” or“No.” In another aspect, the underwriting questions may provide a listof options to select using radio buttons, drop down lists and otherfeatures available on the mobile computing device 20. Once allunderwriting questions have been answered, the user 12 may then resubmitthe information to the insurance company 400 via the POS application 90.

In FIG. 6T, having submitted all relevant and required information, thePOS application 90 has communicated over the network 80 with one or moreinsurance companies 400 and one or more insurance companies 400 haveprovided insurance quotes 415 which have been received by the POSapplication 90. Each quote 415, in one aspect, is presented to the user12 on a new quote page 1440. The user 12 may then elect to either “Save”the displayed quote for future reference, or “Accept” the quote. Inanother aspect, an aggregation 417 of the quotes are transmitted to thePOS application 90 for display to the user 12 for comparison andevaluation.

Referring now to FIG. 6U, once the user 12 has accepted a quote 415, the“Purchase Options” page interface 1450 is displayed to the user 12 bythe POS application 90. Prior to the presentation of the purchaseoptions, in one aspect, the system 10 may have checked the user 12credit history via one of the commercial credit record databases 440.This information may be used to establish credit options or deny credit,requiring payment in full prior to binding the insurance coverage.

Typically, regardless of the purchase option selected by the user 12, aninitial payment may be required. For that purpose, as shown in FIG. 6V,the user is presented with a “Scan Credit Card for Payment” userinterface 1460. As with scanning a driver's license or VIN tag, the user12 will image a credit card by capturing an image of the credit cardwithin the brackets 1467 presented on the displayed user interface 1460.Once the credit card has been imaged, the relevant information isextracted from the textual information and communicated to the insurancecompany using existing well-known methods for processing credit cardpayments. Once the credit card payment has been processed, the POSapplication 90 causes a confirmation of payment interface 1470, shown inFIG. 6W, to be displayed to the user 12. At this interface, the user canelect to view their associated “Virtual ID Card” 1473 or simply “Finish”1475 the transaction. The user 12 is also provided with a phone numberthat can be called directly from this final interface by clicking on thehyperlink which will initiate the call on the phone or across WiFi usingvoice over internet protocols (VOiP).

FIGS. 7A-7E are illustrations of a virtual interactive insuranceidentification card 2000 according to the present invention. Ultimately,all of the information which has been collected for the insurancepurchase transaction is aggregated with information concerning theinsurance policy, its coverage provisions and resources available toaccess those resources. This aggregate information is transformed andassociated with a digital insurance identification card 2100 uponcompletion of an insurance purchase transaction. A “My Virtual ID”button 2110 is presented on the face of the virtual interactiveinsurance identification card 2000. Selecting the button 2110 will causethe “My Virtual ID” interface 2200 to be presented to the user 12.

The POS application 90 will cause the “My Virtual ID” interface 2200 tosupplant the initial login interface associated with the POS application90 as the main interface for the user 12. The My Virtual ID 2200 willprovide an interactive user interface still associated with the POSapplication 90, but primarily directed to access to consumer-centricrequirements after purchase of insurance. Note that an agent using thePOS application 90 would have no need for the My Virtual ID and thus,may not be provided with a My Virtual ID function as described below.

Referring to FIG. 9B, the My Virtual ID is readily accessible through anapplication icon 4200 placed preferably on the home screen of the mobilecomputing device 20. The My Virtual ID application icon 4200 may beselected at the home screen 4000, which will cause the POS application90 to present a virtual interactive insurance identification card(“virtual ID card”) 2000 to the user 12 on the display screen 55 of themobile computing device 20.

Referring to FIG. 7A and FIG. 7B, a front 2100 of the virtual ID 2000contains summary information as well as interactive objects. Forexample, a user 12 may click on the hyperlinked phone number if involvedin an accident. Additionally, the user 12 may select the “My Virtual ID”button 2010. In one aspect, selection of the “My Virtual ID” button 2010causes the virtual ID card 2000 to flip as if exposing a rear 2200 ofthe card. On this new rear page 2200, additional features andfunctionality are accessible to the user 12.

First, via touch selection of the policy icon 2210, the user 12 mayaccess a complete record of all driver, vehicular and insurance policyinformation, which will be displayed in a new policy interface.

Additionally, via touch selection of an accident icon 2220, the usergains access to an accident interface that provides functionality andinformation that will assist the user 12 in the event they have been inan accident.

Next, via touch selection of a roadside assistance icon 2230, the user12 may access roadside assistance via a hyperlinked telephone number ora separate roadside assistance user interface that is in direct digitalcommunication with the appropriate support group of the insurancecompany.

Still further, via touch selection of a dollar sign icon 2240, the user12 may elect to request a new quote to determine if better coverage orlower prices are available.

In addition, via touch selection of a folder icon 2250, the user 12 mayopen a repository where data collected may be stored for future access.The repository can receive images or video from the camera 37 of themobile device 20. The images may include, for example, pictures ofdamage to a vehicle, a video of the location surrounding an accidentsite, images of the placement of vehicles at the accident site, imagesof braking tire marks, images of the driver's license, vehicleregistration certificate and hard copy insurance identification card forany parties involved in the accident, images of the other party involvedin the accident, videos of statements from any witnesses that might beavailable to describe the accident and images of any other aspect thatmight prove useful for future submittal of claims or evidence to supportfault or lack thereof. This information will be time stamped for futurereference as necessary. Upon opening the repository, the user 12 willhave the ability to automatically transmit all relevant information tothe insurance company 400 or legal counsel for their records and use.Data transmittal will be restricted to those parties having a need tohave access or to know the information to support the insured user 12.

Referring to FIG. 7C, an exemplary screen is shown that illustrates theinformation and functionality made available to the user 12 through thevirtual interactive insurance identification card 2000 when an accidentoccurs. The accident interface 2200 provides features and functionalitythat do not require textual keyboard interaction. All aspects that mightbe useful to a user 12 after a collision or other accident areconveniently provided in this accident interface and are accessible viatouch selection. Such aspects include displaying or sending insuranceinformation to another party, accessing roadside assistance, placing acall to an insurance representative, and calling an emergency number.

Referring now to FIG. 7D, in greater detail, an exemplary user interfaceassociated with accessing roadside assistance is shown. This roadsideassistance interface 2300 allows the user 12 to clarify what roadsideassistance may be necessary by selecting any of the buttons 2310 whichdescribe a particular circumstance, such as a flat tire, a dead battery,out of fuel, locked out of the car, report the car stolen or other. Inaddition to providing more specific information for the entity providingroadside assistance to the insured user 12, the user 12 is able to sendtheir location to the insurance carrier via a “My Location” icon 2320.During an accident or when roadside assistance is required, the user 12may not have a accurate awareness of the user's location and it isgenerally preferable to directly send location information to a supportperson, which can then be confirmed with the user 12. Another option isprovided to allow the user 12 to select a “Call InsuranceRepresentative” icon 2330 to call the user's insurance representativedirectly for advice. Finally, an alternative is provided to allow theuser 12 to select an “EMERGENCIES” icon 2340 to call 9-1-1, which willsimultaneously submit location information to the emergency lineoperator.

Referring to FIG. 7E, in an alternative embodiment of the presentinvention directed to the “My Virtual ID” virtual identification card2000, a separate menu interface is provided where touching the MyVirtual ID icon 2110 will cause a radial menu 2500 to extend from theicon presenting symbols consistent with those symbols shown on the rearinterface 2200 for the virtual identification card 2000. Each of theicons associated with the radial menu 2500, which will be generallyconsistent with the icons associated with a rear interface 2200 of theMy Virtual ID card will take the user 12 to the more detailed userinterface associated with that particular icon.

In addition to supporting a consumer-centric version of the system 10along with the creation of the My Virtual ID card, the system 10 alsoprovides a POS application 90 for use by an insurance agent. Referringnow to FIGS. 8A-8L, exemplary user interface screenshots associated witha further embodiment of the invention, wherein the POS application 90 isoperated by an agent rather than the consumer, are shown. FIG. 8A is anillustration of the initial agent interface 3010 for the agent versionof the POS application 90. For clarity, each of the interfacesassociated with the agent version of the POS application 90 areidentified by an “A” in the upper right corner of each displayedinterface. FIG. 8B is an illustration of the agent login interface 3030.FIG. 8C is an illustration of information associated with variousdrivers for a particular account. In this interface 3200, the status ofvarious drivers may be changed to “Excluded” or “Regular.” In addition,a driver 14 may be removed from the list.

In FIG. 8D, an agent interface listing the “Discount Options” 3300 isprovided to the agent/user 12. In FIG. 8E, the agent is presented withan interface that allows selection of a “Policy Term Period” 3400. InFIG. 8F, the agent is presented with an interface providing a list of“Cars Insured” 3500. Additional cars may be added to the coverage fromthis interface. The “Coverages” button 3510 may be selected to presentthe agent with a “Coverages” interface 3600, shown in FIG. 8G, wheretypes and levels of coverage may be selected. In FIG. 8H, the “CarsInsured” interface 3500 for the particular insured party is againdisplayed to the agent. A visual checkmark icon 3520 is displayed toshow that the coverages have been entered and confirmed for theassociated vehicle 16. In FIG. 81, the agent is presented with aninterface 3600 describing details of a quote received and to bepresented to the applicant to “Accept” or reject. In FIG. 8J, additionalcertifications which may be required to allow the requested insurance tobe underwritten are presented to the agent in a form interface 3700 forpresentation to the user where selections can be made. Finally, byselecting the “Sign” arrow 3750, as shown in FIG. 8K, the agent ispresented with a signature field 3800 where a digital signature may beprovided by an applicant using a finger or a stylus. In FIG. 8L,“Payment Information” 3900 is acquired, once again by scanning a creditor debit card which causes the various data fields to be populated.

Referring now to FIGS. 9A-9C, various aspects of icon placement on thehome screen 4000 of the mobile computing device 20 are described. InFIG. 9A, an exemplary illustration of a mobile operating system homescreen 4000 providing access to the consumer-centric POS application 90is shown. A POS application icon 4100 is associated with the firstdownload of the POS application 90 from an app store, such as thoseprovided by APPLE and GOOGLE. Selecting the POS application icon 4100will cause the POS application to execute, allowing a new user 12 toapply to obtain insurance.

In FIG. 9B, an exemplary illustration of a home screen 4000 containingonly the My Virtual ID icon 4200 is shown. According to the presentinvention, once a user 12 has acquired insurance via the system 10, theyare provided with a virtual interactive insurance identification card2000. The My Virtual ID icon 4200 provides immediate access to thevirtual interactive insurance identification card 2000 from the homescreen 4000 of the mobile computing device 20. The virtual interactiveinsurance identification card 2000 now becomes the primary interface foraccess to services which include the services originally available viathe POS application 90 and the additional services provided once theuser 12 has become an insured user. The original consumer-centric POSapplication icon 4100 is removed from the home screen in favor of the MyVirtual ID icon 4200.

In FIG. 9C, an exemplary illustration of a home screen providing accessto an agent-centric version of the POS application 90 is shown. Theagent-centric icon 4300 is associated with the agent-centric POSapplication 90. Selecting the agent-centric icon 4300 will cause theagent-centric POS application 90 to execute to allow an agent to assista consumer in obtaining insurance.

The present invention has been particularly shown and described withrespect to certain preferred embodiments and features thereof. However,it should be readily apparent to those of ordinary skill in the art thatvarious changes and modifications in form and detail may be made withoutdeparting from the spirit and scope of the inventions as set forth inthe appended claims. The inventions illustratively disclosed herein maybe practiced without any element which is not specifically disclosedherein.

What is claimed is:
 1. A vehicular insurance point-of-sale system for amobile user applicant comprising: a. a mobile device; b. extendednetwork architecture and infrastructure accessible by said mobiledevice; c. a point-of-sale software application executable on saidmobile device; and, d. said point-of-sale software applicationconfigured to operate on said mobile device and use one or more featuresof said mobile device such that all input into said point-of-salesoftware application by a user applicant does not require the use of akeyboard interface on a screen of said mobile device.
 2. The vehicularpoint-of-sale system of claim 1 wherein said mobile device includes oneor more input modes comprising: a. a camera; b. a scanner; c. touchinput; d. a numeric keypad; e. audio input; and, f. voice recognition.3. The vehicular point-of-sale system of claim 1 wherein saidpoint-of-sale system leverages one or capabilities of said mobile deviceincluding: a. phone mode; b. voice recorder mode; c. text messagingmode; d. e-mail mode; e. digital camera mode; f. digital video recordingmode; g. photograph gallery mode; h. video gallery mode; and, i. GPSmode.
 4. A method for expediting provision of vehicular insurance quotesto a user via a mobile device to complete an application process,comprising: a. downloading a point-of-sale software application andinstalling said POS application on said mobile device; b. selecting andlaunching said point-of-sale software application; c. a user applicantinputting login credentials and logging in to said point-of-salesoftware application d. said point-of-sale software applicationconfirming a geographic location of the user applicant; e. enteringdriving information into said point-of-sale software application byimaging a driver license using a camera of said mobile device; f.extracting and storing driver information from a scan of the driverlicense; g. presenting said driver information to the user forconfirmation or correction; h. presenting an option for the user to scanadditional driver's licenses; i. repeating steps e through h until alldriver's licenses have been scanned; j. transmitting said driverinformation to a customer information database; k. entering vehicularinformation into said point-of-sale software application by imaging avehicle identification number using said camera of said mobile device;l. extracting and storing said vehicular information from a scan of thevehicle identification number; m. presenting said vehicular informationto the user for confirmation or correction; n. presenting an option forthe user to image additional vehicle identification numbers; o.repeating steps k through n until all vehicle identification numbershave been imaged; p. transmitting said vehicular information to saidcustomer information database; q. confirming a garage address for eachvehicle associated with a vehicle identification number; r. checkingsaid garage address against the user location based on geographicpositioning information provided to said point-of-sale softwareapplication by said mobile device geographic positioning features; s. ifsaid garage address is remote from said user location, reconfirming withthe user that said garage address is correct; t. transmitting saidconfirmation to said customer information database; u. sharing allcustomer information with one or more insurance carriers to allowgeneration of one or more insurance quotes for delivery and presentationto the applicant user via said point-of-sale software application onsaid mobile device; v. prompting the user applicant to select a quotefrom a list of available quotes; w. cancelling the application processif the user applicant does not select a quote; x. prompting the userapplicant to confirm an insurance purchase transaction for a selectedquote; y. presenting payment options to the user applicant; z. the userapplicant selecting a payment option; aa. finalizing the insurancepurchase transaction; bb. recording data associated with said insurancepurchase transaction in said point-of-sale software application; and,cc. sending said data to said customer information database for finalprocessing.
 5. The method of claim 4 further comprising the steps of: a.the point-of-sale software application generating a temporary digitalinsurance identification card to serve as temporary proof of insurance;b. the insurance company issuing the quote accepted by the userapplicant creating an insurance policy binding between the insurancecompany and the user applicant; c. the insurance company authorizing thepoint-of-sale software application to create and display to the userapplicant a permanent digital insurance identification card, confirmingcompletion of said insurance purchase transaction and establishing acontractually-binding policy.
 6. The method of claim 4 furthercomprising the steps of: a. a central server in communication with saidpoint-of-sale software application; b. said central server processingsaid driver information and said vehicular information transmitted tosaid customer information database for use in digitally accessing one ormore third-party data sources containing additional said driverinformation and said vehicular information; c. said central servercombining said additional driver information and said additionalvehicular information from said one or more third-party sources tocreate a user applicant risk profile for use by the insurance company inproviding an insurance quote to the user applicant.
 7. The method ofclaim 7 wherein said one or more third-party data sources are selectedfrom the list of: a. the National Motor Vehicle Title InformationSystem; b. state Department of Motor Vehicle systems; c. police records;d. fire and insurance records; e. credit scoring entities; f. vehiculardata aggregators; and, g. proprietary vehicular and driver data sources.8. The method of claim 4 further comprising: a. said point-of-salesoftware application displaying an icon to an applicant user; b. saidicon triggerable by said applicant user to directly call a data entrysupport person to assist in inputting all necessary information for theuser by speaking with the data entry support person; c. saidpoint-of-sale software application receiving all data inputted by thedata entry support person for display to the applicant user forcorrection and confirmation.
 9. The method of claim 4, furthercomprising the steps of: a. upon finalization of the insurance purchasetransaction process; b. replacing said point-of-sale softwareapplication icon displayed on a screen of said mobile device with anicon representing said permanent digital virtual insuranceidentification card; c. accessing the insured user's information byselecting said icon representing said permanent digital virtualinsurance identification card.
 10. An interactive virtual insuranceidentification card for display via a mobile device comprising: a. adigital front side; b. said digital front side displaying staticinformation and one or more interactive objects; c. a digital rear side;d. said digital rear side displaying static information and one or moreinteractive objects.
 11. The interactive insurance virtualidentification card of claim 10 wherein said interactive objectscomprise: a. a virtual insurance identification button for causing saidinteractive virtual identification card display to flip from saiddigital front side to said digital rear side; b. a hyper-linked phonenumber for contacting an insurance representative; c. a policy icon toprovide a user with access to all policy information; d. an accidenticon to provide a user with access to an accident interface; e. aroadside assistance icon to allow a user to obtain roadside assistancevia a hyperlinked telephone number and other direct digitalcommunication features; f. a dollar sign icon to allow a user to requestan updated insurance quote; and, g. a folder icon for accessing a datarepository.
 12. The interactive virtual insurance identification card ofclaim 10 wherein selecting an icon representing the interactive virtualinsurance identification card triggers the deployment of a radial menuhaving one or more interactive objects for access by a user.
 13. Thesystem of claim 1 wherein said point-of-sale software applicationfurther includes an agent version for use by an insurance agent, saidagent version further comprising: a. an initial agent interface; b. anagent login interface; c. a user account driver interface; d. a discountoptions interface; e. a policy term period interface; f. a cars insuredinterface; g. a coverages interface; h. an applicant quote interface; i.an additional certifications form interface; j. a signature interface;and, k. a payment information interface.